Metering of telecommunications services

ABSTRACT

A configurator is provided that connects with various disparate elements in a telecommunication system. The configurator is adapted to receive a traffic plan that has a plurality of different aspects that are implemented across the disparate elements. The configurator is adapted to generate processing schemas and/or databases that can be used by the disparate elements in order to implement the traffic plan.

FIELD

The present specification relates generally to telecommunications andmore particularly relates to metering of telecommunication services.

BACKGROUND

Hardware advances in computing devices and the networks whichinterconnect those devices has facilitated an explosion in softwareapplications. Applications such as real-time chat, voice and video areincreasingly commonplace and widespread. Voice over Internet Protocol(“VOIP”) telephony allows real-time duplex voice communications to becarried over traditional data channels, potentially obviating the needfor traditional voice channels, without the latency or jitter normallyassociated with the specifications of such data channels.

While somewhat behind wireline networks, wireless networks are alsoincreasing in bandwidth to allow substantially real-time chat, voice andvideo applications to be carried thereover. Likewise, the processingpower of handheld portable devices such as cellular telephones andwireless personal digital assistants can now accommodate suchapplications.

Traditional revenue sources for wireline and wireless networks includevoice telephony and traditional data communications. However, theabove-mentioned advances are confusing the means by which networkoperators are compensated by consumers. For example, traditional voicechannels were configured to be carried over twisted pair coppertelephone wires, yet, technology advances now permit high speed Internetcommunications to be carried over twisted pair. Still further advancesnow permit voice communications to be carried over those Internetconnections. As a result, the subscriber may eschew the underlying voiceservice in favour of the Internet service which now serves to provideboth voice and traditional data connectivity for the subscriber. Thiserodes the underlying revenue base for the wireline carrier, whosebusiness model may depend on charging separate fees for both voice andtraditional data services. Hardware advances now raise the samepossibility of erosion of revenue sources for wireless carriers, whichoriginally offered only wireless voice connectivity but are increasingoffering both voice and data connectivity. However the subscriber may beable to find applications to carry the voice service over the data linkand thereby avoid charges for voice services.

The preceding examples are the tip of the iceberg. Applications such asSkype, Google Maps, You Tube, file sharing services were unforeseenapplications that can radically alter the bandwidth profiles for eachsubscriber, with deleterious effects on bandwidth and quality-of-serviceallocations which did not anticipate these services. The result can be aserious deterioration of quality of service for some subscribers asother subscribers unfairly monopolize all available bandwidth.

To address the foregoing, it is increasingly becoming known to monitorwireless traffic so that it can be classified and further processedaccording to classification, such further processing including thepossibility of blocking the traffic and/or to apply different rates ofcharge according to classification. However, current networkinfrastructures can still be improved. Indeed, one problem is that, evenwithin the current 3GPP or 3GPP2 specifications for differenttelecommunication elements, it can readily arise that configurations forthose elements within one carrier infrastructure are handled in adisparate manner.

SUMMARY

From one perspective, the present specification provides a configuratorthat connects with various disparate elements in a telecommunicationsystem. The configurator is adapted to receive a traffic plan that has aplurality of different aspects that are implemented across the disparateelements. Exemplary aspects include policy aspects and charging aspects.Such a traffic plan can include tariffs, rating rules, pricing,bandwidth, priorities, allow/block indicators, bundling details and caninclude other controls that pertain to the behavior of a subscriber'suse of an application, content, or service. The configurator is adaptedto generate processing schemas and/or databases that can be used by thedisparate elements in order to implement the traffic plan.

From another perspective, the present specification provides a methodfor metering telecommunication services. The method comprises receivinga plurality of variable inputs at a subscriber terminal. Each of inputsrepresent a different metering level for a different application,content, or service. The method also comprises generating a traffic planbased on each metering level. The generated traffic plan can be providedto the configurator or to a similar type component so thattelecommunication services can be delivered according to the trafficplan. The method also comprises generating a representation of thetraffic plan at the subscriber terminal.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic representation of a communication system.

FIG. 2 is a flow-chart depicting a method of configuring a communicationsystem.

FIG. 3 is a schematic representation of a communication system which isa variation on the system of FIG. 1.

FIG. 4 is a schematic representation of the subscriber terminal of FIG.3.

FIG. 5 is a flow-chart depicting a method for metering telecommunicationservices.

FIG. 6 shows the display of the device of FIG. 4 during part of theperformance of the method of FIG. 5.

FIG. 7 is a schematic representation of a communication system which isa variation of the system of FIG. 1.

FIG. 8 is a flow-chart depicting a method for metering telecommunicationservices as a variation on the method of FIG. 5.

FIG. 9 shows the display of the device of FIG. 4 during part of theperformance of the method of FIG. 8.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The following definitions relate to telecommunication structuresreferenced in this specification:

“3GPP Standards” means the Technical Specifications as have beenproduced by the 3rd Generation Partnership Project (3GPP) as updatedfrom time to time.

“3GPP2 Standards” means the Technical Specifications as have beenproduced by the 3rd Generation Partnership Project 2 (3GPP2) as updatedfrom time to time.

“AAA” means Authentication, Authorization and Accounting

“AF” means Application Function as described in 3GPP TS 23.203—“3rdGeneration Partnership Project; Technical Specification Group Servicesand System Aspects; Policy and charging control architecture” as updatedfrom time to time

“AS” means Application Server

“CDR” means Call Detail Record

“DIAMETER protocol” means the computer networking protocol for AAA thatis a successor to RADIUS as generally described by IETF RFC3588—“Diameter Base Protocol” as updated from time to time

“DPI” means Deep Packet Inspection

“GGSN” means GPRS Gateway Service Node as described in 3GPP TS23.203—“3rd Generation Partnership Project; Technical SpecificationGroup Services and System Aspects; Policy and charging controlarchitecture” as updated from time to time

“Gx” means the link and protocol that resides between the PCEF and thePCRF as generally described in 3GPP TS 23.203—“3rd GenerationPartnership Project; Technical Specification Group Services and SystemAspects; Policy and charging control architecture” as updated from timeto time

“Gy” means the link and protocol that resides between the OCS and thePCEF as generally described in 3GPP TS 23.203—“3rd GenerationPartnership Project; Technical Specification Group Services and SystemAspects; Policy and charging control architecture” as updated from timeto time

“GPRS” means General Packet Radio Service

“IETF” means Internet Engineering Task Force

“IMS” means IP Multimedia Subsystem as described in 3GPP TS 23.228—“3rdGeneration Partnership Project; Technical Specification Group Servicesand System Aspects; IP Multimedia Subsystem (IMS); Stage 2” as updatedfrom time to time.

“IP” means Internet Protocol

“ISDN” means Integrated Services Digital Network

“MSISDN” means Mobile Subscriber ISDN Number

“OCS” means Online Charging Server as described in 3GPP TS 23.203—“3rdGeneration Partnership Project; Technical Specification Group Servicesand System Aspects; Policy and charging control architecture” as updatedfrom time to time

“PCC” means Policy and Charging Control as described in 3GPP TS23.228—“3rd Generation Partnership Project; Technical SpecificationGroup Services and System Aspects; IP Multimedia Subsystem (IMS); Stage2” as updated from time to time

“PCEF” means Policy Charging Enforcement Function as described in 3GPPTS 23.203—“3rd Generation Partnership Project; Technical SpecificationGroup Services and System Aspects; Policy and charging controlarchitecture” as updated from time to time

“PCRF” means Policy Charging Rules Function as described in 3GPP TS23.203—“3rd Generation Partnership Project; Technical SpecificationGroup Services and System Aspects; Policy and charging controlarchitecture” as updated from time to time.

“P-CSCF” means Proxy Call Session Control Function as described in 3GPPTS 23.228—“3rd Generation Partnership Project; Technical SpecificationGroup Services and System Aspects; IP Multimedia Subsystem (IMS); Stage2” as updated from time to time

“RADIUS” means Remote Authentication Dial In User Service

“RAT type” means Radio Access Technology type

“Rx” means the link and protocol that resides between the AF and thePCRF as generally described in 3GPP TS 23.203—“3rd GenerationPartnership Project; Technical Specification Group Services and SystemAspects; Policy and charging control architecture” as updated from timeto time

“RFC” means Request for Comments

“SIP” means Session Initiation Protocol

“SCP” means Service Control Point

“SPR” means Subscription Profile Repository as generally described in3GPP TS 23.203—“3rd Generation Partnership Project; TechnicalSpecification Group Services and System Aspects; Policy and chargingcontrol architecture” as updated from time to time

“SIP” identity means canonical SIP Uniform Resource Identifier employedto reach a user or device (such as ‘sip:alice@atlanta.com)’

“SUB ID” means any unique SUB IDentifier. SUB ID can be, for example, aMSISDN or a SIP identity.

Referring now to FIG. 1, a communication system is indicated generallyat 50. System 50 comprises a GGSN 54 operated by a carrier C. GGSN 54interconnects a wireless client device 58 operated by a subscriber S anda server 62. GGSN 54 is based on known GGSN infrastructures, with novelmodifications thereto as will be discussed further below. Those skilledin the art will recognize that the GGSN 54 may be manifested as othernetwork elements in the context of other access technologies. Forexample, a packet serving data node (PDSN) for a code division multipleaccess (CDMA) based network; the IP edge router for a EuropeanTelecommunications Standards Institute (ETSI) based network; the cableModem termination system (CMTS) for a PacketCable based network; aaccess service network (ASN) gateway for a WiMax based network; or adeep-packet inspection node for a generic internet protocol basednetwork.

Wireless client device 58 is associated with a subscriber S and can bebased on any known or future-conceived mobile or nomadic communicationequipment including, for example, a cellular telephone or a wirelesspersonal digital assistant. While not shown herein, it will understoodby those skilled in the art that the wireless client device 58 includesa hardware configuration that may comprise one or more input devices inthe form of a keyboard, microphone and the like; one or more outputdevices in the form of a display, a speaker and the like; a radio forconducting wireless communications; all of which are interconnected by amicrocomputer comprised of one or more central processing units thatitself is connected to volatile memory and non-volatile memory.

Wireless client device 58 connects to GGSN 54 via a first link 66. Firstlink 66 is based on any combination of wireless and wiredinfrastructures that are now-known, or future-conceived, that canconnect wireless client device 58 with GGSN 54. For example, first link66 can conform with a 3GPP infrastructure that includes a wireless basestation that communicates wirelessly with the radio in client device 58,backhaul such as a T1, a mobile switching center, routers and the like.

Server 62 can be based on any known or future-conceived servers,including for example, a web server or any other type of server capableof hosting a service 70 on behalf of client device 58 and for use bysubscriber S. Any type of service 70 is contemplated includingapplications. Examples of services include, but are not limited to,software downloads, web-pages, instant messaging, email, web-mail,mapping services, location applications, social networking services andapplications, file sharing services and applications, peer-to-peerservices, music or video streams or downloads. Thus, it should beunderstood that server 62 can be any other computing device to whichclient device 58 may communicate, including another client device, andthus service 70 can also include peer-to-peer type applicationsincluding voice over IP, and file sharing. While not shown herein, itwill understood by those skilled in the art the server 62 includes ahardware configuration that may comprise one or more input devices inthe form of a keyboard, a mouse and the like; one more output devices inthe form of a display, and the like; a network interface for conductingnetwork communications; all of which are interconnected by amicrocomputer comprised of one or more central processing units thatitself is connected to volatile memory and non-volatile memory.

Server 62 connects to GGSN 54 via a second link 74. Second link 74 isbased on any combination of wireless or wired infrastructures that arenow-known, or future-conceived, that can connect server 62 with GGSN 54.For example, second link 74 can include a 3GPP infrastructure associatedwith GGSN 54 that includes a gateway to a local area network or widearea network that in turn uses a data protocol such as the IP. Likewise,second link 74 can include relevant portions of the Internet associatedwith server 62, which connects to the network interface in server 62.

GGSN 54 itself can be based on any known or future-conceived servershaving a hardware structure that is generally consistent with thehardware structure discussed in relation to server 62 except includingthe appropriate interfaces to connect to link 66 and link 74 and (otherlinks as discussed below as shown in FIG. 1), as well as includingsoftware that configures the server to fulfill the function of a GGSN asprescribed by the relevant 3GPP standards. GGSN 54 is configured toimplement a DPI engine 75. Those skilled in the art will recognize thatthe methods of identifying and classifying distinct subscriber andapplication specific bearer flows are collectively referred to as ‘DeepPacket Inspection’ capabilities. With respect to parametric informationthat is inherent in the bearer data flow that can be used to identifyand classify subscriber or application specific data flows, this mayinclude the source and destination internet protocol addresses, portinformation, protocol information, and other information that conveysthe access technology used (such as the Radio Access Technologyparameter). Information that may be conveyed between the device 58 andthe server 62 may include the application identifier, flow identifiers,and the media type(s) associated with a given service or application. Inaddition to the utilization of explicit addressing or applicationinformation inherent in the data flow or conveyed from external networkelements or application servers, the DPI engine 75 may recognizepatterns or characteristic traffic flows as indicative ‘signatures’ thatare associated with a given service or application. GGSN 54 is alsoconfigured to implement a PCEF 76 as will be discussed further below. Ina present embodiment, DPI engine 75 and PCEF 76 are implemented assoftware processes on GGSN 54, although it is to be understood that theycan be implemented on one or more separate pieces of hardwarefunctionally connected to GGSN 54.

GGSN 54 also connects to an OCS 82 via a third link 86. OCS 82 itselfcan be based on any known or future-conceived servers having a hardwarestructure that is generally consistent with the hardware structurediscussed in relation server to 62 except including the appropriateinterfaces to connect to link 86, as well as including software thatconfigures the server to fulfill the function of an OCS as prescribed inthe 3GPP standards OCS 82 is configured to fulfill charging functions inrelation to the subscriber account associated with subscriber S (such asmaintaining records in association with the MSISDN of device 58) in atleast one of a post-paid and a pre-paid context. In the post-paidcontext OCS 82 is thus configured to generate CDRs that can be used toadd charges to the bill or account of a subscriber. In the pre-paidcontext OCS 82 is thus configured to fulfill the functions of an SCP(and in fact OCS 82 can be implemented as an SCP) that can be used todeduct amounts from a subscriber's prepaid balance. Regardless of thepost-paid or pre-paid context, in a present exemplary embodiment OCS 82is configured to perform such charging in a substantially real-timemanner, whereby as the service is being delivered to subscriber S, thecharges associated with that service are being applied. Third link 86can be based on any physical infrastructure that is suitable forconnecting GGSN 54 to OCS 82 as will now occur to those of skill in theart. For example, third link 86 can be configured to carryingcommunications using the Gy protocol. Those skilled in the art will nowrecognize that the Gy protocol may be manifested as other protocols inthe context of other access technologies. For example, where theanalogous protocol for a code division multiple access (CDMA) basednetwork is generally described in 3GPP2 X.S0013—“All-IP Core NetworkMultimedia Domain” as amended from time to time and where the analogousprotocol for an internet protocol access technology is generallydescribed in ETSI ES 282 003: “Telecommunications and Internet convergedServices and Protocols for Advanced Networking (TISPAN); Resource andAdmission Control Sub-system (RACS) Functional Architecture” as amendedfrom time to time.

GGSN 54 also connects to a PCRF 90 via a fourth link 94. PCRF 90 itselfcan be based on any known or future-conceived servers having a hardwarestructure that is generally consistent with the hardware structurediscussed in relation server to 62 except including the appropriateinterfaces to connect to link 94 as well as including software thatconfigures the server to fulfill the function of a PCRF as prescribed inthe 3GPP standards. PCRF 90 is configured to fulfill tariff decision,bandwidth quality decision and traffic gating decision (collectively thetraffic plan decision) functions which in turn can be used by PCEF 76within GGSN 54 and eventually by OCS 82 in order to determine the actualcharge. PCRF 90 is thus configured to decide traffic policies betweendevice 58 and server 62, including, but not limited to, trafficassociated with the access of service 70 on device 58. Indeed PCRF 90 isconfigured to decide traffic policies on all traffic types carried byGGSN 54. PCRF 90 is also configured to perform such traffic plandecision in substantially real time in order to coordinate with the realtime functionality of OCS 82.

Fourth link 94 can be based on any physical infrastructure that issuitable for connecting GGSN 54 to PCRF 90. In a present embodimentfourth link 94 is configured to communications using the Gx protocol. Ina more general embodiment, fourth link 94 is configured to carrycommunications relative to the final determination of an actual trafficplan decision for a given traffic that is being carried between device58 and server 62.

Those skilled in the art will now recognize that the various protocolsdiscussed herein may be manifested as other protocols in the context ofother access technologies. For example, where the analogous protocolsfor a code division multiple access (CDMA) based network are generallydescribed in 3GPP2 X.S0013—“All-IP Core Network Multimedia Domain” asamended from time to time and where the analogous protocols for aninternet protocol access technology are generally described in ETSI ES282 003: “Telecommunications and Internet converged Services andProtocols for Advanced Networking (TISPAN); Resource and AdmissionControl Sub-system (RACS) Functional Architecture” as amended from timeto time.

PCRF 90 also connects to SPR 102 via fifth link 106. SPR 102 can beimplemented as a file server which includes a microcomputer, a networkinterface and persistent storage in order to maintain data and in orderto allow that data to be accessed by PCRF 90 and any other networkelement that connects to SPR 102. The data that SPR 102 is configured tomaintain includes profile information about subscriber S. Such profileinformation can include, but need not be limited to, an identificationof subscriber S (including for example the MSISDN of device 58), whethersubscriber S is a prepaid or postpaid subscriber, the various types oftraffic that subscriber S is permitted to received on device 58, thevarious rates for any traffic that subscriber S accesses on device 58,including rates for traffic associated with the accessing of service 70on device 58, subscriber preferences such as a preferred quality ofservice to be associated with accessing a given service 70 via device58, and subscriber or network operator imposed limitations such as anupper bound on the total bandwidth consumed by subscriber S via device58.

Fifth link 106 can be based on any desired physical link and protocol inorder to communicate subscriber profile data to PCRF 90. It should nowbe apparent that SPR 102 can be implemented within PCRF 90, or it can besituated remotely from PCRF 90 so that a plurality of different PCRFs(not shown) and other network elements can centrally access profile datarelative to subscriber 102.

System 50 also comprises a plurality of storage devices 110, 114 and118. As can be seen in FIG. 1, storage device 110 is connected to OCS 82and is therefore configured to maintain data usable by OCS 82 to permitOCS 82 to fulfill its functions. Likewise, storage device 114 isconnected to PCRF 90 and is therefore configured to maintain data usableby PCRF 90 to permit PCRF 90 to fulfill its functions. Likewise, storagedevice 118 is connected to SPR 102 and is therefore configured tomaintain data usable by SPR 102 to permit SPR 102 to fulfill itsfunctions. It should now be apparent that each storage device 110, 114and 118 can be implemented, if desired, as a component within itsrespective component.

It can also be noted at this point that storage devices 110, 114 and 118each maintain using different data structures, and that some of thosedata structures can be common amongst all storage devices 110, 114 and118, while some of those data structures can be disparate amongst allstorage devices 110, 114 and 118. The common data structures can arisebecause aspects of those storage devices are constrained by therequirements 3GPP Standards. The fact The different data structures canarise because aspects of those storage devices will be constrained byunique specifications of the carrier C that defines the domain in whichGGSN 54, PCRF 90, OCS 82 and SPR 102 are operated. Alternatively, oradditionally, the fact that different specifications for data structureshave arisen can result from the fact that GGSN 54, PCRF 90, OCS 82 andSPR 102 may themselves be designed according to different specifications(e.g. one or more of GGSN 54, PCRF 90, OCS 82 and SPR 102 may beprovided by different originating equipment manufacturers each withtheir own unique “flavor” or variation.) Alternatively, or additionally,the fact that different specifications for data structures have arisencan result from the fact that GGSN 54, PCRF 90, OCS 82 and SPR 102 mayhave been deployed at different times and according to differentprograms and therefore the data structures associated therewith havebeen specified differently.

Notwithstanding the specific examples above, it should now be understoodthat in general each storage device 110, 114, and 118 needs to maintaindata that is consistent with the other storage devices 110, 114 and 118;but each storage device 110, 114 and 118 can also have extra data thatis not found at the other storage devices 110, 114 and 118. Therefore,all storage device 110, 114, and 118 have to be synchronized accordingto the specific configuration detail they each need to hold. (Thoseskilled in the art will now recognize that in FIG. 1 GGSN 54, PCRF 90,OCS 82, SPR 102 and the associated storage devices 110, 114 and 118 areenclosed within the dashed enclosed area indicated at reference C, whichrepresents the carrier C that operates those components. It should alsonow be understood however that carrier C is a simplified example andthat those skilled in the art will recognize how a variation of system50 can accommodate the components within carrier C being operated bymultiple carriers to accommodate roaming scenarios).

System 50 also comprises a configurator 122 that connects to each ofGGSN 54, PCRF 90, OCS 82 and SPR 102. As will be discussed furtherbelow, configurator 122 is configured to receive a traffic plan forsubscribers and to automatically deploy that plan amongst GGSN 54, PCRF90, OCS 82 and SPR 102 such that GGSN 54, PCRF 90, OCS 82 and SPR 102will be configured to implement said traffic plan.

Configurator 122 can be implemented using known computing environmentshaving appropriate network interfaces to connected with GGSN 54, PCRF90, OCS 82 and SPR 102. Such a computing environment could be based on acommercial server that includes a microprocessor and volatile storage.The volatile storage can be implemented as random access memory (“RAM”)and can be used to temporarily store applications and data as they arebeing used by processor. Configurator 122 also includes read only memory(“ROM”) connected to the microprocessor which contains a basic operatingsystem containing rudimentary programming instructions, commonly knownas a Basic Input/Output System (“BIOS”) that are executable by themicroprocessor when configurator 122 is initially powered so that ahigher level operating system and applications can be loaded andexecuted on processor. Collectively, one can view the processor,volatile storage device and ROM as a microcomputer. It should now beapparent that configurator 122 can be based on the structure andfunctionality of a commercial server such as a Sun Fire X4450 Serverfrom Sun Microsystems Inc., of Palo Alto, USA, but it is to be stressedthat this is a purely exemplary server, as configurator 122 could alsobe based on any type of computing device including from othermanufacturers.

Referring now to FIG. 2, a communication method represented in the formof a flow-chart is indicated generally at 200. Method 200 can beimplemented using system 50 or functionally equivalent modified versionsof system 50. To help provide further understanding relative to method200 and system 50, method 200 will be discussed in relation to exemplaryperformance of method 200 using system 50.

At block 205, a traffic plan is received. Block 205 is performed atconfigurator 122 which can receives a data file representing a trafficplan. The mean by which the plan is received is not particularlylimited, and can occur, for example, via a user operating a computerterminal that is connected to configurator 122, whereby the user entersin data via a graphical user interface that represents the traffic plan.

In the present exemplary embodiment the traffic plan is unique to a setof subscribers, including subscriber S, that are associated with trafficplans being offered by carrier C. It should be understood that trafficpolicies for any number of subscribers S associated with carrier C arecontemplated.

The traffic plan includes a plurality of aspects. In a presentembodiment, the traffic plan is based on the 3GPP standards andtherefore includes charging aspects and policy aspects, where thecharging aspects are aspects respective to OCS 82, and the policyaspects are aspects respective to PCRF 90 and SPR 102, and both chargingaspects and policy aspects respective to GGSN 54. Table I shows asimplified example of a traffic plan, which includes entries that areunique to subscriber S.

TABLE I Exemplary contents of Traffic plan Field 3 Field 5 Field 6 Field7 Field 8 Field 1 Field 2 Bit Field 4 Usage Billing Basic Roaming EntrySUB ID Service Rate Volume Period Arrangement Rate Rate 1 S VT1—VOIP 115kbps 100 MB Day Postpaid $10.00/MB $30.00/MB tel 1 2 S TC1—Text  1 kbpsUnlimited Unlimited Postpaid $2.00/MB $3.00 MB chat 1 3 S MS1—Music  25kbps 50 songs Day Postpaid $1.00/song $2.00/song stream 1

Explaining the structure of Table I in greater detail, Field 1 entitled“SUB ID”, is an identifier that can be used uniquely identify asubscriber (e.g. subscriber S). The identifier can either be specific toa device (such as device 58), or to each specific subscriber (such assubscriber S) contemplating that each subscriber could authenticate withdifferent computing devices and still be subject to the same trafficplan. (While not discussed herein, where subscribers are permitted toauthenticate with different computing devices, then policy P could befurther enriched, beyond what is shown in Table I, to vary the policyaccording to the computing device, or even the nature of linksconnecting the device to network 58). Field 2 of Table I, entitled“Service” identifies the various types of services that are subject tothe traffic plan. As will be explained in greater detail below, servicescan include any type of service that is currently known or as yetunknown, including voice telephony, chat, video streaming, musicstreaming and so on. Field 3 of Table I, entitled “Bit Rate” is themaximum permitted bit rate associated with a particular service. Field 4of Table I, entitled “Volume” is the maximum amount of data that can bedownloaded to device 70 and uploaded from device 70. Field 5, of TableI, entitled “Usage Period” defines the period during which the volumedefined in Field 4 is measured. That is to say where usage periodindicates “Day” and Volume indicates “1 MB”, then the subscriber will bepermitted one Megabyte of data transfer during one day. Field 6, ofTable I, entitled “Excess Permitted” defines whether the subscriber ispermitted to exceed the limits defined in Fields 4 and 5. Such excessmay be permitted should the subscriber S agree to be subject toincreased billing rates, and/or the sacrifice of limits for otherservices, and/or some other consideration in exchange for beingpermitted to exceed the limits defined in Fields 4 or 5. Those skilledin the art will recognize that Fields 3, 4, and 5 can be each dividedinto two separate fields, one for up-stream traffic from device 70 tonetwork 58 and the other for downstream traffic from network 58. Field 6of Table I, entitled “Billing Arrangement” indicates whether aparticular service is on a post paid or prepaid basis. Field 7 entitled“Basic Rate” indicates the rate that is charged for a particular serviceif that particular subscriber accesses that service from within carrierC's coverage area, and according to the corresponding data in Fields 3,4 and 5. Field 8 entitled “Roaming Rate” indicates the rate that ischarged for a particular service if that subscriber S does not thatservice from within carrier C's coverage area, but instead within thecoverage are of another carrier.

Explaining each exemplary service in greater detail, “VT1—VOIP tel 1” inField 2, Entry 1 identifies a VOIP telephony service that is offered bya first service provider. For example “VT1—VOIP tel 1” could be the wellknown VOIP application Skype, available at http://www.skype.com.“TC1—Text chat 1” in Field 2, Entry 2 identifies a “chat” service thatis offered by a first service provider. For example “TC1—Text chat 1”could be the well known chat application, Google Talk, available athttp://google.com. “MS1—Music stream 1” in Field 2, Entry 3 identifies astreaming audio application that is offered by a first service provider.For example “MS1—Music stream 1” could be based on the well knownweb-site Pandora, available at http://www.pandora.com. Each of theseservices will be ascertainable by DPI engine 75 as part of its regularfunction.

It should now be understood that any type of service can be included inTable I, such as peer-to-peer, video services, mapping services. Also acatchall “unknown” service can also be provided where a particularservice is being carried that is not ascertainable by DPI engine 75.

It should now be reemphasized that Table I is a non-limiting example,and one of the features of the specification is the inherent flexibilityprovided by system 50. Carrier C is able to define any traffic plan thatis desired and provide that traffic plan to configurator 122.

At block 210 the traffic plan from block 205 is parsed. As part of thisblock, configurator 122 will analyze the field structures within Table Iand determine which fields are relevant to GGSN 54, PCRF 90, OCS 82 andSPR 102. At a general level, at block 210 configurator will parse thetraffic plan according to which portion of the traffic plan is relevantto the policy aspects of the traffic plan, and which port of the trafficplan is relevant to the charging aspects of the traffic plan. Table IIshows which fields are applicable to the policy aspects or chargingaspects or both.

TABLE II Fields in Traffic plan Applicable to Different Aspects Field 3Field 5 Field 6 Field 7 Field 8 Field 1 Field 2 Bit Field 4 UsageBilling Basic Roaming SUB ID Service Rate Volume Period Arrangement RateRate Applicable Both Both Policy Both Policy Charging Charging ChargingTo: policy policy aspect policy aspect Aspect Aspect Aspect and and andcharging charging charging aspects aspects aspects

Moving beyond this general analysis, configurator 122 also maps eachfield to the appropriate element (e.g. GGSN 54, PCRF 90, OCS 82 and SPR102). Thus, continuing with the present example Table III.

TABLE III Fields in Traffic plan Applicable to Different Elements Field5 Field 6 Field 7 Field 8 Field 1 Field 2 Field 3 Field 4 Usage BillingBasic Roaming Element SUB ID Service Bit Rate Volume Period ArrangementRate Rate GGSN 54 Y Y Y Y Y N N N PCRF 90 Y Y Y Y Y N N N SPR 102 Y Y YY Y N N N OCS 82 Y Y N Y N Y Y Y

Explaining Table III in greater detail, various flags are provided whichindicate whether a particular field in Table I are applicable to each ofGGSN 54, PCRF 90, OCS 82 and SPR 102. Where a particular field isrelevant, then that field will be used as part of creating a sub-planfor that component. For example, Field 1, SUB ID is indicated as beingrelevant for each of GGSN 54, PCRF 90, OCS 82 and SPR 102 as part ofdeploying the traffic plan in Table I across GGSN 54, PCRF 90, OCS 82and SPR 102. However, Field 7 Billing Arrangement is only applicable toOCS 82.

At block 215, a sub-plan for each element is generated. Block 215 isalso performed by configurator 122, which generates a sub-plan for eachelement.

Beginning with the first element in Table III (GGSN 54) configurator 122can provide a processing schema for use by GGSN 54 in the application ofthe traffic plan from Table I. Table IV shows an example of a processingschema that can be generated for GGSN 54 as part of block 215

TABLE IV Processing schema for use by GGSN 54 SUB ID Service Bit RateVolume Usage Period (Field 1 from Table I) (Field 2 from Table I) (Field3 from Table I) (Field 4 from Table I) (Field 5 from Table I) 1. ObtainSUB ID from device 58 as part of monitoring 1. Obtain bit rate cap 1.Obtain volume 1. Obtain usage period access to service 70. as part ofpolicy cap as part of restrictions as part 2. Obtain Service type ofservice 70 using DPI Engine 75. information from PCRF policy from PCRFof policy from PCRF 90 3. Forward SUB ID and service type to PCRF 90 toobtain 90 respective to SUB 90 respective to respective to SUB bit rate,volume and usage period policy information ID and Service. SUB ID andService. ID and service. 1. Forward SUB ID and service type to OCS 82 toobtain permission 2. If permission granted by OCS 82, permit service 70applying bit rate, volume and usage period restrictions. 3. Record usageof service 70 by SUB ID in view of bit rate, volume and usage periods.4. Forward results or recorded usage to OCS 82.

Thus, the processing schema in Table IV can be deployed at block 220 toGGSN 54 in order to configure GGSN 54 to operate in accordance with thetraffic plan in Table I, such that accessing of service 70 by subscriberS is permitted in accordance with the traffic plan of Table I.

Returning again to block 215, turning now to the second element in TableIII (PCRF 90) configurator 122 can provide a processing schema for useby PCRF 90 in the application of the traffic plan from Table I. Table Vshows an example of a processing schema that can be generated for PCRF90 as part of block 215.

TABLE V Processing schema for use by PCRF 90 SUB ID Service Bit RateVolume Usage Period (Field 1 from Table I) (Field 2 from Table I) (Field3 from Table I) (Field 4 from Table I) (Field 5 from Table I) 1. ObtainSUB ID from GGSN 54. 1. Obtain bit rate cap 1. Obtain volume 1. Obtainusage period 2. Obtain Service type from GGSN 54. as part of policy capas part of restrictions as part 3. Access policy information relativeinformation from SPR policy from SPR of policy from SPR 102 to same fromSPR 102 102 respective to SUB 102 respective to respective to SUB ID andService. SUB ID and Service. ID and service. 1. Forward bit rate cap,volume cap and usage period restrictions to GGSN 54.

Thus, the processing schema in Table V can be deployed at block 220 toPCRF 90 in order to configure PCRF 90 to operate in accordance with thetraffic plan in Table I, such that accessing of service 70 by subscriberS is permitted in accordance with the traffic plan of Table I.

Returning again to block 215, turning now to the third element in TableIII (SPR 102) configurator 122 can provide a policy and processingschema for use by SPR 102 in the application of the traffic plan fromTable I. Table VI shows an example of a policy that can be generated aspart of block 215.

TABLE VI Contents of Policy to be stored at SPR 102 Field 1 Field 5Subscrib- Field 2 Field 3 Field 4 Usage Entry er ID Service Bit RateVolume Period 1 S VT1 - VOIP 115 kbps 100 MB Day tel 1 2 S TC1 - Text  1kbps Unlimited Unlimited chat 1 3 S MS1 - Music  25 kbps 50 songs Daystream 1

Thus, the database in Table VI can be deployed at block 220 to SPR 102in order to maintain a policy that reflects the policy aspects of TableI. Table VII shows an example of a processing schema that can begenerated for SPR 102 as part of block 215.

TABLE VII Processing schema for use by SPR 102 SUB ID Service Bit RateVolume Usage Period (Field 1 from Table I) (Field 2 from Table I) (Field3 from Table I) (Field 4 from Table I) (Field 5 from Table I) 1. ObtainSUB ID from PCRF 90. 1. Obtain bit rate cap 1. Obtain volume cap 1.Obtain usage period 2. Obtain Service type from PCRF 90. for subscriberand for subscriber and restrictions for 3. Access policy informationrelative particular service from particular service subscriber andparticular to same from Table VI. Table VI. from Table VI. service fromTable VI. 1. Forward bit rate cap, volume cap and usage periodrestrictions to PCRF 90

Thus, the processing schema in Table VII can be deployed at block 220 toSPR 102 in order that SPR 102 processes requests from PCRF 90 in amanner that reflects the policy aspects of Table I.

Returning again to block 215, turning now to the fourth element in TableIII (OCS 82) configurator 122 can provide a charging database and aprocessing schema for use by OCS 82 in the application of the trafficplan from Table I. Table VIII shows an example of a charging databasethat can be generated for PCRF 90 as part of block 215.

TABLE VIII Contents of Charging Database to be stored at OCS 82 SUB IDService Billing arrangement Basic Rate Roaming Rate Entry (Field 1 fromTable I) (Field 2 from Table I) (Field 6 from Table I) (Field 7 fromTable I) (Field 8 of Table I) 1 S VT1 - VOIP tel 1 Postpaid $10.00/MB$30.00/MB 2 S TC1 - Text chat 1 Postpaid  $2.00/MB  $3.00 MB 3 S MS1 -Music stream 1 Postpaid  $1.00/song  $2.00/song

Thus, the database in Table VIII can be deployed at block 220 to OCS 90in order to maintain a charging database that reflects the chargingaspects of Table I. Table IX shows an example of a processing schemathat can be generated for OCS 82 as part of block 215.

TABLE IX Processing schema for use by OCS 82 SUB ID Service Billingarrangement Basic Rate Roaming Rate (Field 1 from Table I) (Field 2 fromTable I) (Field 6 from Table I) (Field 7 from Table I) (Field 8 of TableI) 1. Obtain SUB ID from GGSN 54. 1. Generate billing records 1.Determine if 1. Determine if 2. Obtain Service type from GGSN 54.according to billing subscriber is subscriber is 3. Permit or denypermission to use service based arrangement. For pre-paid using basicroaming, and, if on charging records associated with SUB IDarrangements, deduct from rate, and, if so, so, apply charges pre-paidaccount. For post- apply charges based on roaming paid arrangement, addtotal based on basic rate. charge to subscriber bill. rate.

Thus, the processing schema in Table IX can be deployed at block 220 toOCS 82 in order to configure OCS 82 to operate in accordance with thetraffic plan in Table I, such that accessing of service 70 by subscriberS is permitted in accordance with the traffic plan of Table I.

When system 50 is configured according to method 200 using Table I, theusage of service 70 by subscriber S will be performed in accordance withthe traffic plan of Table I. In operation, assume that service 70 isVT1—VOIP Tel 1. When subscriber S attempts to access service 70, DPIengine 75 within GGSN 54 will inspect the packets forming the request toaccess service 70, and will ascertain that subscriber S using device 58is attempting to access service 70. In turn, GGSN 54 will utilize theprocessing schema of Table IV to access PCRF 90 to obtain policyinformation relative to the terms of use of service 70 by subscriber S.

In turn, PCRF 90 will utilize the processing schema of Table V in orderto ascertain the relevant policy information. In using the processingschema of Table V, PCRF 90 will access SPR 102. SPR 102 will in turn usethe processing schema of Table VII and access the policy in Table VI toobtain the relevant policy information for VT1—VOIP tel 1, in order toascertain a bit-rate cap of 115 kbps with a maximum volume of 100megabytes per day. SPR 102 will return this policy information to PCRF90 which will forward that policy information back to GGSN 54. GGSN 54,still utilizing the processing schema in Table IV, will now access OCS82 which will use its own processing schema from Table IX coupled withthe charging database in Table VIII to perform the charging aspectfunction of the traffic plan of Table I. If OCS 82 instructs that itpermits access, GGSN 54 will (continuing to apply the processing schemaof Table IV) permit subscriber S to access service 70, sendingappropriate charging information back to OCS 82.

Those skilled in the art will now recognize that the traffic plan inTable I has now been implemented using the foregoing teachings, suchthat accessing of service 70 by subscriber S is permitted in accordancewith the traffic plan of Table I. Advantageously, configurator 122 hasprovided a central location for receiving the traffic plan andautomatically configured the various elements of system 50 to implementthe traffic plan. This permits carrier C to modify the traffic plan atany time without having to individually update GGSN 54, PCRF 90, SPR 102and OCS 82 to respond to such modifications.

Those skilled in the art will also recognize that the Configurator canalso apply the traffic plan to other network elements including, butlimited to, the Mobile Switching Center Service Capability InteractionManager (SCIM), and the Call Session Control Function (CSCF) as well asvalue added service platforms such as the Multimedia Messaging ServiceCenter (MMS-C), Application Server, Wireless Application Protocol (WAP)Gateway, Short Message Service Center (SMS-C), Unified Messaging Server,and content (e.g. music or video) distribution servers.

The nature and scope of such service profile criteria information is notparticularly limited. For example, traffic plan criteria can include aflag indicating that access of service 70 is not permitted whatsoever bydevice 58 such that device 58 will be prevented access to service 70.Where access to service 70 is permitted according to the traffic plancriteria, then the traffic plan criteria can include rating information,which can include complex criteria, such as, at least one of: times ofday, week or month that access to service 70 is restricted or prevented;tiered rates of charge for accessing service 70 depending on the time ofday service 70 is being accessed; maximum bandwidth allocationsassociated with access to service 70; maximum amounts of data that canbe accessed from service 70; tiers of rates associated with higherbandwidths or capacities; tiers of rates associated with whether device58 is roaming or within its home network; privacy management thatanonymizes certain data carried between device 58 and service 70; flatrate charges for unlimited access to service 70; and combinations of anyof the foregoing. Other traffic plan criteria will now occur to those ofskill in the art. Indeed, traffic plan criteria can be found in theApplicants' co-pending application number PCT/CA2007/001528 and entitledPolicy Services, the contents of which are incorporated herein byreference.

While the foregoing describes certain specific embodiments, it is to bereemphasized that those embodiments are exemplary and can be modifiedand that variations, subsets and combinations of those embodiments arecontemplated. Indeed, it is to be reemphasized that the specificexamples of processing schemas and databases are simplified for ease ofexplanation. But it should be understood that the database format ofTable I, and the database formats and schema formats of the other Tablescan vary according to the specific computing environments used toimplement each of the components in system 50, and thereforeconfigurator 122 can in turn be structured to accommodate such specificcomputing environments. As a still further example, the teachings ofPCT/CA2007/001528 can be incorporated into the teachings herein.

Referring now to FIG. 3, a communication system in accordance withanother embodiment is indicated generally at 50 a. System 50 a is avariation on system 50 and therefore components in system 50 a that havelike components in system 50 bear the same reference character in bothsystems, except that in system 50 a the reference character is followedby the suffix “a”.

Of note is that system 50 a includes a subscriber terminal 300 a whichconnects to configurator 122 a via a network 304 a. In a present, purelyexemplary, embodiment network 304 a is the Internet. Subscriber terminal300 a is based on the functionality of desktop computing device thatincludes at least networking capabilities. Many well known desktopcomputing devices, or variants thereof, are suitable for the presentembodiment. Referring now to FIG. 4, a schematic block diagram of eachsubscriber terminal 300 a is shown. It should be emphasized that thestructure in FIG. 4 is purely exemplary, and contemplates a device thatcan be used for Internet communications over network 304 a. Subscriberterminal 300 a includes a plurality of input devices, which in a presentembodiment includes a keyboard 400 and a microphone 404. Other inputdevices, such as a microphone are also contemplated. Input from keyboard400 and mouse 404 is received at a processor 408, which in turncommunicates with a non-volatile storage unit 442 (e.g. read only memory(“ROM”), Erase Electronic Programmable Read Only Memory (“EEPROM”),Flash Memory) and a volatile storage unit 446 (e.g. random access memory(“RAM”)). Programming instructions that implement the functionalteachings of subscriber terminal 300 a as described herein are typicallymaintained, persistently, in non-volatile storage unit 442 and used byprocessor 408 which makes appropriate utilization of volatile storage446 during the execution of such programming instructions. Variants onsubscriber terminal 300 a can include a laptop computer equipped withwireless capabilities. It will become apparent that even device 58 a canserve the function as subscriber terminal 300 a, thereby obviating theneed for a separate subscriber terminal 300 a.

Subscriber terminal 300 a is configured to operate as a web-browser andtherefore a web-browser application 436 is maintained in non-volatilestorage 442 in order to permit subscriber S to operate subscriberterminal 300 a and perform web-browsing functions. Also of note insystem 50 a is that configurator 122 a is configured to operate aweb-server to host web-browsing sessions on subscriber terminal 300 a.

Referring now to FIG. 5, a method for metering of telecommunicationservices is indicated in the form of a flow-chart generally at 500.Method 500 (or variants thereof) can be used, if desired, prior toinvocation of method 200 (or a variation thereof), such that the trafficplan referenced at block 520 can be all or part of the traffic planintroduced at block 205.

At block 505, inputs are received representing metering levels. In apresent exemplary embodiment, block 505 can be performed by theweb-server executing on configurator 122 a in conjunction with theweb-browser application 436 executing on subscriber terminal 300 a. Inother words, a graphical user interface can be generated on subscriberterminal 300 a which receives inputs from subscriber S that representmetering levels and which are in turn received at the web-server onconfigurator 122 a.

FIG. 6 shows an example graphical user interface (GUI) 450 that can behosted by configurator 122 a for generation on display 420. GUI 450, viaprocessor 408, is responsive to inputs from keyboard 400 and mouse 404.GUI 450 comprises a volume section, a quality of service section, analert section and a pricing section.

The volume section outlines maximum amounts of data that can bedownloaded to device 58 a and uploaded from device 58 a for variousservices. The volume selection is generally analogous in concept toField 4 of Table I. In general, note that that the metering levels inFIG. 6 do not correspond exactly to the various levels that can formpart of a tariff plan as discussed in relation to system 50. Thisdifference is intended illustrate that different types andconfigurations of tariff plans and the constituent elements thereof arecontemplated. The volume section comprises a plurality of sliders 454-1,454-2, 454-3, 454-4, 454-5, 454-6, 454-7 (collectively, sliders 454 andgenerically, slider 454. This nomenclature is used elsewhere). Slidersare graphical representations of electro-mechanical rheostats. Eachslider 454 is respective to a different service and can be used toselect a different maximum amount of data that can be downloaded and/oruploaded in a given month. Slider 454-1 thus can be used to provideinput representing maximum amount of data that can be downloaded and/oruploaded in a given month for a web-browsing service. Slider 454-2 thuscan be used to provide input representing maximum amount of data(between zero and one Gigabyte) that can be downloaded and/or uploadedin a given month for a VoIP service that is hosted by carrier C. Slider454-3 thus can be used to provide input representing maximum amount ofdata (between zero and two-hundred megabytes) that can be downloadedand/or uploaded in a given month for a VoIP service that is hosted bycarriers other than carrier C. Slider 454-4 thus can be used to provideinput representing maximum amount of data (between zero and five-hundredmegabytes) that can be downloaded and/or uploaded in a given month foran IP Media Sharing service (e.g. Bittorrent or other peer to peer filesharing service). Slider 454-5 thus can be used to provide inputrepresenting maximum amount of data (between zero and one-hundredmegabytes) that can be downloaded and/or uploaded in a given month foran Instant Messaging service hosted by carrier C (e.g. Bittorrent orother peer to peer file sharing service). Slider 454-6 thus can be usedto provide input representing maximum amount of data (between zero andone-hundred megabytes) that can be downloaded and/or uploaded in a givenmonth for an Instant Messaging service hosted by a carrier other thancarrier C (e.g. Bittorrent or other peer to peer file sharing service).Slider 454-7 thus can be used to provide input representing maximumamount of data (between zero and fifty megabytes) that can be downloadedand/or uploaded in a given month for a gaming service (e.g. an onlinevideo game such as poker which is played via multiple devices likedevice 58 which are also connected to carrier C).

It should also be understood that the volume section, can, in otherembodiments express different, or additional volume metrics, such as anevent count (e.g. number of instant messages), minutes (e.g. maximumnumber of minutes of VoIP calling). Other volume metrics will now occurto those of skill in the art. Each slider 454 can also be configured toreflect a different volume metric.

Furthermore, as another variation, each slider 454 can be configured toshow a representation of the exact amount of volume that is currentlyselected by that particular slider 454. In this variation, each slider454 would have a current value depicted in the slider which changes inreal time as that slider 454 is slid up and down. The values within eachslider 454 can be configured to be editable within the slider itself, sothat one can simply enter the text, for example, “50 Mb” instead ofhaving to accurately move it up and down to achieve 50 Mb.

GUI 450 can also be modified, for other embodiments, to have multiplescreens, whereby “double-clicking” (or other selecting technique) on aparticular slider 454 could invoke another GUI that provides granulardetail about a particular service. For example, gaming slider 454-7could be configured to be selectable so that another GUI is invoked (notshown in the Figures) on screen 420 with an additional set of sliders,and each of those sliders could be configured to reflect individualgames, which in their aggregate would be capped by the volume selectedaccording to slider 454-7 on GUI 450. The quality of service section ofGUI 450 comprises a plurality of switches 458. Each switch 458 isrespective to a slider 454 and the associated service. Switches 458 are,in a present example, graphical representations of 3-wayelectromechanical switches. Each switch 458 can be set to define aquality of service level for a particular service. In the presentexample, each switch 458 has three positions, labeled “B” for Bronze;“S” for Silver; and “G” for Gold. Bronze level of service would be thelowest quality of service level, while silver would be an intermediatequality of service level, and gold would be the highest quality ofservice level. Each quality of service level would generally reflect amaximum bit rate (generally analogous to Field 3 of Table I). Thoseskilled in the art will recognize that each switch 458 can be manifestedvia an alternative control (for example, a slider) that provides for afiner degree of granularity in terms of defining the quality of servicelevel for a particular service.

The alert section of GUI 450 comprises a plurality of radio-boxes 459that simply indicate “Y” for “Yes” or “N” for No. The radio-boxes, whenset to “Y” indicate that a message is to be sent to device 58 whendevice 58 reaches (or nears) the maximum volume indicated in the maximumvolume section. GUI 450 can be modified so that alert section alsoincludes a volume metric that indicates the exact volume of consumptionwhich will trigger the delivery of the alert to device 58. The alertsection could be modified to be an automatic quality of serviceadjustment. The identification of a volume metric in the alert sectioncould thus be used (in lieu of or in addition to the actual alertnotification) as part of generation of the tariff plan at block 520,whereby a quality of service selection at switch 450 would beautomatically dropped to the next lower setting once the selected volumein the alert section is reached, thereby deferring the reaching of thethreshold value in exchange for a reduction in quality of service.

Note that GUI 450 can be implemented different combinations of sliders,switches or radio-boxes or other interactive graphics that can be usedto provide the input contemplated at block 505 of method 500.

At block 510, a tariff plan representation is generated based on theinputs received at block 505. In a present exemplary embodiment, block510 is also performed by the web-server executing on configurator 122 ain conjunction with the web-browser application 436 executing onsubscriber terminal 300 a. In a present embodiment, the graphical userinterface in FIG. 6 is also used as part of the implementation of block510, whereby a representation of the tariff plan is generated onsubscriber terminal 300 a based on determinations made at configurator122 a.

Block 510 is implemented via the pricing section of GUI 450, whichcomprises a pie-graph 462 that includes a dial-pointer 466 thatindicates the total monthly price of a subscription that has a tariffplan that is implemented in accordance with the inputs provided involume section, quality-of-service section and alert section. Also note,in the present exemplary embodiment, pie-graph 462 has two portions: abasic package portion 470 and an enhanced package portion 474. Basicpackage portion 470 is filled with hatching, while enhanced packageportion 474 is filled with cross-hatching. Such hatching andcross-hatching, it will be appreciated, can be effected with differentcolours rather than hatching and cross-hatching. Note that the hatchingin basic package portion 470 corresponds to hatching on sliders 454-1,454-2 and 454-5, while the cross-hatching in enhanced package portion474 corresponds to cross-hatching on sliders 454-3, 454-4, 454-6 and454-7. Thus, pie-graph 462 indicates which portion of the tariff plan isattributable to basic services (i.e. those services associated withsliders 454-1, 454-2 and 454-5) and which portion of the tariff plan isattributable to enhanced services (i.e. those services associated withsliders 454-3, 454-4, 454-6 and 454-7). It will be appreciated that whatis designated “basic services” vs “enhanced services” can be determinedby carrier C, and so designated in such a manner to encourage the use of“basic services” vs “enhanced services”, or to make clear thatadditional charges are being levied for “enhanced services” due to thefact that they are more costly for carrier C to implement.

Note that while pie-graph 462 comprises two portions 470 and 474, GUI450 can be modified to have only one portion or to have more than oneportion. For example, pie-graph 462 could be configured to have sevenportions, with one portion being respective to each slider 454.Furthermore, pie-graph 462 can be further segmented into furtherportions, with such additional portions configured to show which portionof the pie-graph 462 is attributable to a particularly quality ofservice respective to switches 458.

Thus, in a typical scenario, the position of dial-pointer 466 will pointto higher prices as any one or more of sliders 454 are raised. Likewise,the position of dial-pointer 466 will point to lower prices as any oneor more of sliders 454 are lowered. Also, the position of dial-pointer466 will point to higher prices as any one or more of switches 458 areincreased from a lower quality of service level to a higher quality ofservice level. Likewise, the position of dial-pointer 466 will point tolower prices as any one or more any one or more of switches 458 aredecreased to a lower quality of service level from a higher quality ofservice level. Pricing can also be changed according to whether or notany of the radio-boxes are selected.

Also of note, is that the size of basic package portion of 470 willincrease or decrease according to changes to sliders 458-1, 458-2 and458-5 or switches 458-1, 458-2, and 458-5, while the size of enhancedpackage portion of 474 will increase or decrease according to changes tosliders 454-3, 454-4, 454-6 and 454-7 or switches 458-3, 458-4, 458-6and 458-7.

In another variation, dial-pointer 466 can itself be configured to beselectable and movable, so that selecting and moving dial-pointer 466towards a lower value can automatically cause corresponding sliders 454and/or switches 458 to likewise lower. Conversely, moving dial-pointer466 towards a higher value can automatically cause corresponding sliders454 and/or switches 458 to likewise raise. As a still further variation,dial-pointer 466 can be configured so that individual sliders 458 and/orswitches 458 can be “locked” in a given position, so that movingdial-pointer 466 will only cause corresponding movement in those sliders458 and/or switches 458 which are not “locked”. As a still furthervariation, dial-pointer 466 can be configured to be “locked”, inaddition to the ability to “lock” sliders 454 and/or switches 458, sothat movement of one unlocked slider 454 or switch 458 will only causecorresponding movement in those sliders 454 or switches 458 that areunlocked.

Referring again to FIG. 5, at block 515 a determination is made as towhether the plan is accepted. In a present embodiment, and referring nowto FIG. 6, the determination of whether or not the plan is accepted isbased on whether or not a selection button 478 is selected (via forexample a selection and click of mouse 404). If selection button 478 isnot selected then method 500 cycles back to block 505. If selectionbutton 478 is selected then method 500 advances to block 520.

At block 520, a tariff plan is generated based on the inputs from block505. The resulting tariff plan can perform the input for block 205 ofmethod 200. At this point, however, it is to be reiterated that thespecific services and associated options for the tariff plans that canbe selected through the exemplary GUI 450 are not intended to beidentical to the exemplary services and associated options for thetariff plans shown in Table I. In fact, each has different examples inorder to illustrate the configurability associated with the teachingsherein.

It should now be understood that method 500 need not be limited tosystem 50 a, and that indeed method 500 and GUI 450 can be used topermit subscribers S to provide input representing desired home orbusiness tariff plans for other types of data services, including homeor business Internet access through wired services (e.g. T1, T3,Fibre-optic, Community Access TeleVision (CATV) coaxial links, DigitalSubscriber Line (DSL)) or wireless services (WiMax, Universal MobileTelecommunications Service, Enhanced Data Rates for GSM Evolution(EDGE)). Referring now to FIG. 7, an example of another communicationsystem that can be used with method 500 is indicated generally at 50 b.System 50 b is a variation on system 50 a and therefore components insystem 50 b that have like components in system 50 a bear the samereference character in both systems, except that in system 50 b thereference character is followed by the suffix “b” instead of “a”.

Of note is that system 50 b is a much simplified version of system 50 aand is based on a wired configuration. Link 66 b is based on DSL, CATV,T1 or T3 (though it can be based on a wireless link). Carrier C operatesany generic gateway equipment 54 b (instead of GGSN 54 a or GGSN 54)that can connect link 66 b to Internet 304 b. Carrier C is an InternetService Provider for subscriber station 300 b. Subscriber station 300 bcan be used to access Internet 304 b, but can also be used to accessconfigurator 122 b in order to perform method 500 b. Configurator 122 bis a simplified abstraction of configurator 122 in that configurator 122b is intended to generically cooperates with gateway equipment 54 b toimplement the tariff plan, and cooperating in a manner that iscomplementary to the functionality of gateway equipment 54 b. Note thatthe billing functions of system 50 b are omitted for simplifiedconvenience, but that configurator 122 b and gateway 54 b likewiseinteract with such billing functions.

As a still further variation, GUI 450 can be modified to includeradio-buttons, a drop-down box or other selection means that permits theselection of a number of pre-set tariff plans (not shown). Uponselection of one of the pre-set tariff plans, each slider 454, switch458, radio-boxes 459, pig-graph 462 and dial-pointer 466 will move to apredefined location on GUI 450. In this modified embodiment, atariff-plan with particular setting can be established with minimalinput, or a predefined tariff plan can be tweaked to reflect uniquepreferences. As an example, a “basic” package and an “enhanced” packagecould be offered as pre-set plans. In this example, FIG. 6 could reflectthe “enhanced” package, while selection of the “basic” package wouldcause: sliders 454-3, 454-4, 454-6 and 454-7 to drop to zero;dial-pointer 466 to point to the fifteen-pounds marker; and enhancedpackage portion 474 to disappear.

Still further variations are contemplated. FIG. 8 shows a method formetering of telecommunication services is indicated in the form of aflow-chart generally at 500 a, which is a variation on method 500. FIG.9 shows another example graphical user interface GUI 450 a, which is avariation on GUI 450. GUI 450 a is configured for use in conjunctionwith method 500 a. Method 500 a includes substantially the same blocksas method 500 and thus like blocks bear like references, except followedby the suffix “a”. GUI 450 a includes substantially the same componentsas GUI 450 and thus like components bear like references, exceptfollowed by the suffix “a”. Of note is that method 500 a includes twoextra blocks: Block 507 a is a decision block whereby a determination ismade as to whether the tariff plan will allow sponsorships to subsidizethe tariff plan; block 508 a is arrived at from the “yes” branch ofblock 507 a, whereby inputs are received relative to acceptedsponsorship levels. To implement the functionality of block 507 a, GUI450 a comprises a permit sponsorship selection button 480 a. Toimplement functionality of block 508 a, GUI 450 a comprises asponsorship section with a plurality of sponsorship level switches 481a, with each switch 481 a respective to a slider 454 a.

Permit sponsorship selection button 480 a can be implemented in a toggleor on/off fashion, whereby if toggled “on” then switches 481 a becomeinteractive and if toggled “off” then switches 481 a becomenon-interactive (perhaps disappearing altogether or becoming “greyed”).In a present embodiment, switches 481 a have three settings: N whichrepresents “no” sponsorship; “P” which represents “partial” sponsorship;and “F” which represents “full” sponsorship. No sponsorship means thatno sponsorship is used to subsidize the service; partial sponsorshipmeans that the service is partially subsidized, while full sponsorshipmeans that the service is fully subsidized. A partially subsidizedservice could refer to, for example, in the context of VoIP, the playingof an audio advertisement prior to the connection of a voice call. Asanother example of a partially subsidized service, a video streamingservice could be paused at periodic intervals for the playing of one ormore video sponsorship messages. At the completion of the videosponsorship message(s), the video streaming service would resume. Afully subsidized service could refer to, for example, in the context ofGaming, the streaming of a banner across the screen 420 during entireplaying of any particular game. Note in the example shown in FIG. 9,that switches 481 a-1, 481 a-2, and 481 a-5 are set to “N” for nosponsorship, while the remaining switches 481 a are set to “P” forpartial sponsorship. Note that since switches 481 a-1, 481 a-2, and 481a-5 are set to “N”, and that those same switches 481 a-1, 481 a-2, and481 a-5 relate to basic package portion 470 a, that basic packageportion 470 a is unchanged from basic package portion 470. However,since switches 481 a-3, 481 a-4, 481 a-6, and 481 a-7 are set to “P”,and that those switches 481 a-3, 481 a-4, 481 a-6 and 481 a-7 relate toenhanced package portion 474 a, that enhanced package portion 474 a hasbeen reduced in half in relation to enhanced package portion 474. Thoseskilled in the art will recognize that switches 481 a can be manifestedvia alternative controls (for example, sliders) that provide for a finerdegree of granularity in terms of defining the level of sponsorship fora particular service.

It should be understood that the foregoing teachings can be combinedwith the teachings of Applicant's co-pending U.S. patent applicationSer. No. 11/744,588 entitled “SYSTEM AND METHOD FOR PROVIDING CONTEXTBASED SERVICES” filed May 4, 2007.

Further variations, combinations and subsets of the foregoingembodiments will now occur to those skilled in the art.

The novel teachings herein can provide certain advantages. For example,where elements in system are produced by different vendors or have beendeployed using separate specifications, configurator 122 can be deployedso as to automatically accommodate such differences to facilitateefficient deployments of different traffic plans. The teachings hereincan satisfy this need.

All documents referenced are incorporated herein by reference.

1. A communication system comprising: at least one element forinterconnecting a client device and a server for hosting a service; saidelement for implementing a traffic plan; said traffic plan forregulating access of said service by said client device; a configuratorconnected to said element and to a subscriber terminal; saidconfigurator adapted to receive inputs from said subscriber terminalrepresenting a proposed version of said traffic plan; said configuratorfurther adapted to generate a representation of said proposed version onsaid subscriber terminal; said configurator further adapted to continuereceiving said inputs and generating said representation based onvariations of said proposed version until an indication is received fromsaid subscriber terminal that said traffic plan is accepted, whereuponsaid configurator generates said traffic plan.
 2. The communicationsystem of claim 1 wherein said elements include one or more of a GGSN, aPCRF, an SPR and an OCS.
 3. The communication system of claim 1 whereinsaid elements include one or more of a Mobile Switching Center, CallSession Control Function, Service Capability Interaction Manager (SCIM),Application Server, Multimedia Messaging Service Center (MMS-C),Application Server, Wireless Application Protocol (WAP) Gateway, ShortMessage Service Center (SMS-C), Unified Messaging Server, and content(e.g. music or video) distribution servers.
 4. The communication systemof claim 2 wherein traffic plan includes said policy aspects that arerespective to said PCRF and said SPR.
 5. The communication system ofclaim 2 wherein said traffic plan includes charging aspects that arerespective to said OCS.
 6. The communication system of claim 1 whereinsaid service is one of software downloads, web-pages, instant messaging,email, web-mail, mapping services, location applications, socialnetworking services and applications, file sharing services andapplications, peer-to-peer services, music or video streams ordownloads.
 7. The communication system of claim 1 wherein said elementsare configured to connect said client device to a plurality of differentservers hosting different servers and said traffic plan is forregulating access to each of said services.
 8. The communication systemof claim 7 wherein said services include at least one of softwaredownloads, web-pages, instant messaging, email, web-mail, mappingservices, location applications, social networking services andapplications, file sharing services and applications, peer-to-peerservices, music or video streams or downloads.
 9. A configurator inaccordance claim
 1. 10. A method for configuring a communication systemcomprising: receiving inputs representing a proposed traffic plan at aconfigurator; generating a representation of said proposed traffic planbased on said inputs; repeating the foregoing steps until an indicationis received that said proposed traffic plan is accepted and thereupon,generating a traffic plan based on said inputs, said traffic plan forregulating access of at least one service by a client device.
 11. Themethod according to claim 10 wherein one of said traffic plan comprisespolicy aspects and a charging aspects.
 12. The method according to claim10 wherein said elements include one or more of a GGSN, ServiceCapability Interaction Manager (SCIM), a PCRF, an SPR and an OCS. 13.The method of claim 10 wherein said elements include one or more of aMobile Switching Center, Call Session Control Function, ApplicationServer, Multimedia Messaging Service Center (MMS-C), Application Server,Wireless Application Protocol (WAP) Gateway, Short Message ServiceCenter (SMS-C), Unified Messaging Server, and content (e.g. music orvideo) distribution servers.
 14. The method according to claim 11wherein said policy aspects are respective to a PCRF and said SPR. 15.The method according to claim 11 wherein said charging aspects arerespective to an OCS.
 16. The method according to claim 10 wherein saidservice is one of software downloads, web-pages, instant messaging,email, web-mail, mapping services, location applications, socialnetworking services and applications, file sharing services andapplications, peer-to-peer services, music or video streams ordownloads.
 17. The method according to claim 10 wherein said elementsare configured to connect said client device to a plurality of differentservers hosting different services and said traffic plan is forregulating access to each of said services.
 18. The method according toclaim 17 wherein said services include at least one of softwaredownloads, web-pages, instant messaging, email, web-mail, mappingservices, location applications, social networking services andapplications, file sharing services and applications, peer-to-peerservices, music or video streams or downloads.
 19. The method accordingto claim 10 wherein said inputs are received via a graphical userinterface, said graphical user interface comprising input valuesrespective to different types of services.
 20. The method according toclaim 19 wherein said representation is generated on said graphical userinterface to indicate a total price for a traffic plan based on saidinputs.
 21. The method according to claim 19 wherein said inputs areprovided using at least one of sliders, switches and radio boxes. 22.The method of claim 19 wherein said input values represent at least oneof maximum volume and quality of service for each of said types ofservices.
 23. The method of claim 19 wherein said maximum volume isrespective to a given period of time.
 24. The method of claim 19 whereinsaid different types of services includes a first class of services anda second class of services.
 25. The method of claim 24 wherein saidfirst class of services is basic services and said second class ofservices is enhanced services.
 26. The method of claim 24 wherein saidrepresentation is generated on said graphical user interface andindicates a total price for a traffic plan based on said inputs andfurther indicates which portion of said price is associated with saidfirst class of services and which portion of said price is associatedwith said second class of services.
 27. The method of claim 19 whereinsaid input values include a representation of whether to send an alertas to whether a maximum volume has been reached under said traffic plan.28. The method according to claim 10 wherein said inputs include said atleast one services.